Method and apparatus for random access configuration in a wireless communication system

ABSTRACT

A method and apparatus are disclosed from the perspective of a User Equipment (UE), wherein the UE is configured with multiple Bandwidth Parts (BWPs). In one embodiment, the method includes the UE receiving information from a network node to associate a RACH (Random Access Channel) configuration with a BWP among the multiple BWPs. The method further includes that the UE performing a RACH transmission in the BWP using the RACH configuration associated with the BWP.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present Application claims priority to and is a continuation of U.S.application Ser. No. 16/058,717, filed on Aug. 8, 2018, entitled “METHODAND APPARATUS FOR RANDOM ACCESS CONFIGURATION IN A WIRELESSCOMMUNICATION SYSTEM”, which claims the benefit of U.S. ProvisionalPatent Application Ser. No. 62/547,373 filed on Aug. 18, 2017. Theentire disclosure of U.S. application Ser. No. 16/058,717 and the entiredisclosure of U.S. Provisional Patent Application Ser. No. 62/547,373are incorporated herein in their entirety by reference.

FIELD

This disclosure generally relates to wireless communication networks,and more particularly, to a method and apparatus for random accessconfiguration in a wireless communication system.

BACKGROUND

With the rapid rise in demand for communication of large amounts of datato and from mobile communication devices, traditional mobile voicecommunication networks are evolving into networks that communicate withInternet Protocol (IP) data packets. Such IP data packet communicationcan provide users of mobile communication devices with voice over IP,multimedia, multicast and on-demand communication services.

An exemplary network structure is an Evolved Universal Terrestrial RadioAccess Network (E-UTRAN). The E-UTRAN system can provide high datathroughput in order to realize the above-noted voice over IP andmultimedia services. A new radio technology for the next generation(e.g., 5G) is currently being discussed by the 3GPP standardsorganization. Accordingly, changes to the current body of 3GPP standardare currently being submitted and considered to evolve and finalize the3GPP standard.

SUMMARY

A method and apparatus are disclosed from the perspective of a UserEquipment (UE), wherein the UE is configured with multiple BandwidthParts (BWPs). In one embodiment, the method includes the UE receivinginformation from a network node to associate a RACH (Random AccessChannel) configuration with a BWP among the multiple BWPs. The methodfurther includes that the UE performing a RACH transmission in the BWPusing the RACH configuration associated with the BWP.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a wireless communication system according toone exemplary embodiment.

FIG. 2 is a block diagram of a transmitter system (also known as accessnetwork) and a receiver system (also known as user equipment or UE)according to one exemplary embodiment.

FIG. 3 is a functional block diagram of a communication system accordingto one exemplary embodiment.

FIG. 4 is a functional block diagram of the program code of FIG. 3according to one exemplary embodiment.

FIG. 5 is a diagram according to one exemplary embodiment.

FIG. 6 is a diagram according to one exemplary embodiment.

FIG. 7 is a flow chart according to one exemplary embodiment.

FIG. 8 is a flow chart according to one exemplary embodiment.

FIG. 9 is a flow chart according to one exemplary embodiment.

FIG. 10 is a flow chart according to one exemplary embodiment.

DETAILED DESCRIPTION

The exemplary wireless communication systems and devices described belowemploy a wireless communication system, supporting a broadcast service.Wireless communication systems are widely deployed to provide varioustypes of communication such as voice, data, and so on. These systems maybe based on code division multiple access (CDMA), time division multipleaccess (TDMA), orthogonal frequency division multiple access (OFDMA),3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A orLTE-Advanced (Long Term Evolution Advanced), 3GPP NR (New Radio), 3GPP2UMB (Ultra Mobile Broadband), WiMax, or some other modulationtechniques.

In particular, the exemplary wireless communication systems devicesdescribed below may be designed to support one or more standards such asthe standard offered by a consortium named “3rd Generation PartnershipProject” referred to herein as 3GPP, including: TR 38.802 v14.1.0,“Study on new Radio Access Technology; Physical layer aspects (Release14)”; TS 36.331 v14.2.0, “E-UTRA; RRC protocol specification (Release14)”; TS 36.211 v14.3.0, “E-UTRA; Physical channels and modulation(Release 14)”; TR 38.804 v14.0.0, “Study on New Radio Access Technology;Radio Interface Protocol Aspects (Release 14)”; TS 36.304 V14.2.0,“E-UTRA; UE procedures in idle mode”; TS 36.321 V14.1.0, “E-UTRA; MACprotocol specification”; TS 36.322 V14.1.0, “E-UTRA; RLC protocolspecification”; and TS 36.323 V14.1.0, “E-UTRA; PDCP protocolspecification”. The standards and documents listed above are herebyexpressly incorporated by reference in their entirety.

FIG. 1 shows a multiple access wireless communication system accordingto one embodiment of the invention. An access network 100 (AN) includesmultiple antenna groups, one including 104 and 106, another including108 and 110, and an additional including 112 and 114. In FIG. 1, onlytwo antennas are shown for each antenna group, however, more or fewerantennas may be utilized for each antenna group. Access terminal 116(AT) is in communication with antennas 112 and 114, where antennas 112and 114 transmit information to access terminal 116 over forward link120 and receive information from access terminal 116 over reverse link118. Access terminal (AT) 122 is in communication with antennas 106 and108, where antennas 106 and 108 transmit information to access terminal(AT) 122 over forward link 126 and receive information from accessterminal (AT) 122 over reverse link 124. In a FDD system, communicationlinks 118, 120, 124 and 126 may use different frequency forcommunication. For example, forward link 120 may use a differentfrequency then that used by reverse link 118.

Each group of antennas and/or the area in which they are designed tocommunicate is often referred to as a sector of the access network. Inthe embodiment, antenna groups each are designed to communicate toaccess terminals in a sector of the areas covered by access network 100.

In communication over forward links 120 and 126, the transmittingantennas of access network 100 may utilize beamforming in order toimprove the signal-to-noise ratio of forward links for the differentaccess terminals 116 and 122. Also, an access network using beamformingto transmit to access terminals scattered randomly through its coveragecauses less interference to access terminals in neighboring cells thanan access network transmitting through a single antenna to all itsaccess terminals.

An access network (AN) may be a fixed station or base station used forcommunicating with the terminals and may also be referred to as anaccess point, a Node B, a base station, an enhanced base station, anevolved Node B (eNB), or some other terminology. An access terminal (AT)may also be called user equipment (UE), a wireless communication device,terminal, access terminal or some other terminology.

FIG. 2 is a simplified block diagram of an embodiment of a transmittersystem 210 (also known as the access network) and a receiver system 250(also known as access terminal (AT) or user equipment (UE)) in a MIMOsystem 200. At the transmitter system 210, traffic data for a number ofdata streams is provided from a data source 212 to a transmit (TX) dataprocessor 214.

In one embodiment, each data stream is transmitted over a respectivetransmit antenna. TX data processor 214 formats, codes, and interleavesthe traffic data for each data stream based on a particular codingscheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot datausing OFDM techniques. The pilot data is typically a known data patternthat is processed in a known manner and may be used at the receiversystem to estimate the channel response. The multiplexed pilot and codeddata for each data stream is then modulated (i.e., symbol mapped) basedon a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM)selected for that data stream to provide modulation symbols. The datarate, coding, and modulation for each data stream may be determined byinstructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TXMIMO processor 220, which may further process the modulation symbols(e.g., for OFDM). TX MIMO processor 220 then provides N_(T) modulationsymbol streams to N_(T) transmitters (TMTR) 222 a through 222 t. Incertain embodiments, TX MIMO processor 220 applies beamforming weightsto the symbols of the data streams and to the antenna from which thesymbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. N_(T)modulated signals from transmitters 222 a through 222 t are thentransmitted from N_(T) antennas 224 a through 224 t, respectively.

At receiver system 250, the transmitted modulated signals are receivedby N_(R) antennas 252 a through 252 r and the received signal from eachantenna 252 is provided to a respective receiver (RCVR) 254 a through254 r. Each receiver 254 conditions (e.g., filters, amplifies, anddownconverts) a respective received signal, digitizes the conditionedsignal to provide samples, and further processes the samples to providea corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the N_(R) receivedsymbol streams from N_(R) receivers 254 based on a particular receiverprocessing technique to provide N_(T) “detected” symbol streams. The RXdata processor 260 then demodulates, deinterleaves, and decodes eachdetected symbol stream to recover the traffic data for the data stream.The processing by RX data processor 260 is complementary to thatperformed by TX MIMO processor 220 and TX data processor 214 attransmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use(discussed below). Processor 270 formulates a reverse link messagecomprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message is then processed by a TX data processor 238, whichalso receives traffic data for a number of data streams from a datasource 236, modulated by a modulator 280, conditioned by transmitters254 a through 254 r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system250 are received by antennas 224, conditioned by receivers 222,demodulated by a demodulator 240, and processed by a RX data processor242 to extract the reserve link message transmitted by the receiversystem 250. Processor 230 then determines which pre-coding matrix to usefor determining the beamforming weights then processes the extractedmessage.

Turning to FIG. 3, this figure shows an alternative simplifiedfunctional block diagram of a communication device according to oneembodiment of the invention. As shown in FIG. 3, the communicationdevice 300 in a wireless communication system can be utilized forrealizing the UEs (or ATs) 116 and 122 in FIG. 1 or the base station (orAN) 100 in FIG. 1, and the wireless communications system is preferablythe NR system. The communication device 300 may include an input device302, an output device 304, a control circuit 306, a central processingunit (CPU) 308, a memory 310, a program code 312, and a transceiver 314.The control circuit 306 executes the program code 312 in the memory 310through the CPU 308, thereby controlling an operation of thecommunications device 300. The communications device 300 can receivesignals input by a user through the input device 302, such as a keyboardor keypad, and can output images and sounds through the output device304, such as a monitor or speakers. The transceiver 314 is used toreceive and transmit wireless signals, delivering received signals tothe control circuit 306, and outputting signals generated by the controlcircuit 306 wirelessly. The communication device 300 in a wirelesscommunication system can also be utilized for realizing the AN 100 inFIG. 1.

FIG. 4 is a simplified block diagram of the program code 312 shown inFIG. 3 in accordance with one embodiment of the invention. In thisembodiment, the program code 312 includes an application layer 400, aLayer 3 portion 402, and a Layer 2 portion 404, and is coupled to aLayer 1 portion 406. The Layer 3 portion 402 generally performs radioresource control. The Layer 2 portion 404 generally performs linkcontrol. The Layer 1 portion 406 generally performs physicalconnections.

3GPP standardization activities on next generation (i.e. 5G) accesstechnology have been launched since March 2015. The new radio accesstechnology aims to support the following three families of usagescenarios for satisfying both the urgent market needs and the morelong-term requirements set forth by the ITU-R IMT-2020:

-   eMBB (enhanced Mobile Broadband)-   mMTC (massive Machine Type Communications)-   URLLC (Ultra-Reliable and Low Latency Communications).

3GPP RAN1 has agreed to introduce the concept of bandwidth part (BWP) inNR. According to 3GPP TR 38.802, resource allocation for datatransmission for a UE not capable of supporting the carrier bandwidthcan be derived based on a two-step frequency-domain assignment process,i.e., indication of a bandwidth part (the 1st step) and indication ofthe PRBs within the bandwidth part (2nd step).

3GPP RAN1 has also reached some agreements with respect to the bandwidthpart as follows:

Agreements:

-   -   Resource allocation for data transmission for a UE not capable        of supporting the carrier bandwidth can be derived based on a        two-step frequency-domain assignment process        -   1^(st) step: indication of a bandwidth part        -   2^(nd) step: indication of the PRBs within the bandwidth            part        -   FFS definitions of bandwidth part        -   FFS signaling details    -   FFS the case of a UE capable of supporting the carrier bandwidth        Agreement:    -   For single-carrier operation,        -   UE is not required to receive any DL signals outside a            frequency range A which is configured to the UE            -   The interruption time needed for frequency range change                from frequency range A to a frequency range B is TBD            -   Frequency ranges A & B may be different in BW and center                frequency in a single carrier operation                Working assumption:    -   One or multiple bandwidth part configurations for each component        carrier can be semi-statically signalled to a UE        -   A bandwidth part consists of a group of contiguous PRBs            -   Reserved resources can be configured within the                bandwidth part        -   The bandwidth of a bandwidth part equals to or is smaller            than the maximal bandwidth capability supported by a UE        -   The bandwidth of a bandwidth part is at least as large as            the SS block bandwidth            -   The bandwidth part may or may not contain the SS block        -   Configuration of a bandwidth part may include the following            properties            -   Numerology            -   Frequency location (e.g. center frequency)            -   Bandwidth (e.g. number of PRBs)        -   Note that it is for RRC connected mode UE        -   FFS how to indicate to the UE which bandwidth part            configuration (if multiple) should be assumed for resource            allocation at a given time        -   FFS neighbour cell RR            Agreements:

-   Confirm the WA of RAN1#88bis.

-   Each bandwidth part is associated with a specific numerology    (sub-carrier spacing, CP type)    -   FFS: slot duration indication if RAN1 decides to not to        downselect between 7 symbol and 14 symbols for NR slot duration

-   UE expects at least one DL bandwidth part and one UL bandwidth part    being active among the set of configured bandwidth parts for a given    time instant.    -   A UE is only assumed to receive/transmit within active DL/UL        bandwidth part(s) using the associated numerology        -   At least PDSCH and/or PDCCH for DL and PUCCH and/or PUSCH            for UL            -   FFS: down selection of combinations    -   FFS if multiple bandwidth parts with same or different        numerologies can be active for a UE simultaneously        -   It does not imply that it is required for UE to support            different numerologies at the same instance.        -   FFS: TB to bandwidth part mapping

-   The active DL/UL bandwidth part is not assumed to span a frequency    range larger than the DL/UL bandwidth capability of the UE in a    component carrier.

-   Specify necessary mechanism to enable UE RF retuning for bandwidth    part switching    Agreement:    -   For FDD, separate sets of bandwidth part (BWP) configurations        for DL & UL per component carrier        -   The numerology of DL BWP configuration is applied to at            least PDCCH, PDSCH & corresponding DMRS        -   The numerology of UL BWP configuration is applied to at            least PUCCH, PUSCH & corresponding DMRS    -   For TDD, separate sets of BWP configurations for DL & UL per        component carrier        -   The numerology of DL BWP configuration is applied to at            least PDCCH, PDSCH & corresponding DMRS        -   The numerology of UL BWP configuration is applied to at            least PUCCH, PUSCH & corresponding DMRS        -   For UE, if different active DL and UL BWPs are configured,            UE is not expected to retune the center frequency of channel            BW between DL and UL            Agreement:    -   At least one of configured DL BWPs includes one CORESET with        common search space at least in primary component carrier    -   Each configured DL BWP includes at least one CORESET with        UE-specific search space for the case of single active BWP at a        given time        -   In case of single active BWP at a given time, if active DL            BWP does not include common search space, then UE is not            required to monitor the common search space            Agreement:    -   In configuration of a BWP,        -   A UE is configured with BWP in terms of PRBs.            -   The offset between BWP and a reference point is                implicitly or explicitly indicated to UE.                -   FFS for reference point, e.g., center/boundary of NR                    carrier, channel number used for sync. and/or                    channel raster, or center/boundary of RMSI BW,                    center/boundary of SS block accessed during the                    initial access, etc.    -   NR supports MU-MIMO between UEs in different (but overlapping)        BWPs        Agreements:    -   Activation/deactivation of DL and UL bandwidth parts can be        -   by means of dedicated RRC signaling            -   Possibility to activate in the bandwidth part                configuration        -   by means of DCI (explicitly and/or implicitly) or MAC CE            [one to be selected]            -   by means of DCI could mean                -   Explicit: Indication in DCI (FFS: scheduling                    assignment/grant or a separate DCI) triggers                    activation/deactivation                -   Separate DCI means DCI not carrying scheduling                    assignment/grant                -   Implicit: Presence of DCI (scheduling                    assignment/grant) in itself triggers                    activation/deactivation                -   This does not imply that all these alternatives are                    to be supported.        -   FFS: by means of timer        -   FFS: according to configured time pattern

New Radio (NR) random access procedure in physical layer is described in3GPP TR 38.802 as follows:

8.2.1 Random Access Procedure

8.2.1.1 Preamble

-   NR defines that    -   a random access preamble format consists of one or multiple        random access preamble(s),    -   a random access preamble consists of one preamble sequence plus        CP, and    -   one preamble sequence consists of one or multiple RACH OFDM        symbol(s)-   UE transmits PRACH according to the configured random access    preamble format.-   NR supports multiple RACH preamble formats, including at least RACH    preamble formats with longer preamble length and shorter preamble    length. Multiple/repeated RACH preambles in a RACH resource are    supported. Numerology for RACH preamble can be different depending    on frequency ranges. Numerology for RACH preamble can be different    from or the same as that for the other UL data/control channels.-   For a single RACH preamble transmission, CP/GT are required. For    example, the single RACH preamble would be used when Tx/Rx beam    correspondence held at both TRP and UE for multi-beam operation.-   For single/multi-beam operation, the following multiple/repeated    RACH preamble transmission is at least supported.    -   CP is inserted at the beginning of the consecutive        multiple/repeated RACH OFDM symbols, CP/GT between RACH symbols        is omitted and GT is reserved at the end of the consecutive        multiple/repeated RACH symbols-   The region for PRACH transmission is aligned to the boundary of    uplink symbol/slot/subframe. For supporting various coverage and    forward compatibility, flexibility in the length of CP/GT and the    number of repeated RACH preambles and RACH symbols is supported Note    that specific use of the RACH preamble transmission may depend on    RACH subcarrier spacing and TRP beam correspondence.    8.2.1.2 Procedure-   RACH procedure including RACH preamble (Msg. 1), random access    response (Msg. 2), message 3, and message 4 is assumed for NR from    physical layer perspective. Random access procedure is supported for    both IDLE mode and CONNECTED mode UEs. For 4-step RACH procedure, a    RACH transmission occasion is defined as the time-frequency resource    on which a PRACH message 1 is transmitted using the configured PRACH    preamble format with a single particular tx beam-   RACH resource is also defined as a time-frequency resource to send    RACH preamble. Whether UE needs to transmit one or multiple/repeated    preamble within a subset of RACH resources can be informed by    broadcast system information, e.g., to cover gNB RX beam sweeping in    case of NO Tx/Rx beam correspondence at the gNB.-   Regardless of whether Tx/Rx beam correspondence is available or not    at gNB at least for multiple beams operation, the following RACH    procedure is considered for at least UE in idle mode. Association    between one or multiple occasions for DL broadcast channel/signal    and a subset of RACH resources is informed to UE by broadcast system    information or known to UE. Based on the DL measurement and the    corresponding association, UE selects the subset of RACH preamble    indices. UE Tx beam(s) for preamble transmission(s) is selected by    the UE. During a RACH transmission occasion of single or    multiple/repeated preamble(s) as informed by broadcast system    information, UE uses the same UE Tx beam. NR at least supports    transmission of a single Msg.1 before the end of a monitored RAR    window.-   At least for the case without gNB Tx/Rx beam correspondence, gNB can    configure an association between DL signal/channel, and a subset of    RACH resources and/or a subset of preamble indices, for determining    Msg2 DL Tx beam. Based on the DL measurement and the corresponding    association, UE selects the subset of RACH resources and/or the    subset of RACH preamble indices. A preamble index consists of    preamble sequence index and OCC index, if OCC is supported. Note    that a subset of preambles can be indicated by OCC indices.-   Regardless of whether Tx/Rx beam correspondence is available or not    at gNB at least for multiple beams operation, at gNB, the DL Tx beam    for message 2 can be obtained based on the detected RACH    preamble/resource and the corresponding association. UL grant in    message 2 may indicate the transmission timing of message 3. As    baseline UE behavior, UE assumes single RAR reception within a given    RAR window.-   At least for UE in idle mode, UL Tx beam for message 3 transmission    is determined by UE. UE may use the same UL Tx beam used for message    1 transmission.-   Different PRACH configurations will be supported, e.g., considering    different numerologies case and whether Tx/Rx beam correspondence is    available or not at gNB.-   For NR RACH Msg. 1 retransmission at least for multi-beam operation,    NR supports power ramping. If UE doesn't change beam, the counter of    power ramping keeps increasing. Note that UE may derive the uplink    transmit power using the most recent estimate of path loss. Whether    UE performs UL Beam switching during retransmissions is up to UE    implementation. Note that which beam UE switches to is up to UE    implementation.

In LTE, configurations of RACH or PRACH are specified in 3GPP TS 36.331as follows:

-   PRACH-Config-   The IE PRACH-ConfigSlB and IE PRACH-Config are used to specify the    PRACH configuration in the system information and in the mobility    control information, respectively.

PRACH-Config Information Elements

-- ASN1START PRACH-ConfigSIB ::= SEQUENCE {  rootSequenceIndex   INTEGER(0..837),  prach-ConfigInfo   PRACH-ConfigInfo } PRACH-ConfigSIB-v1310::=  SEQUENCE {  rsrp-ThresholdsPrachInfoList-r13  RSRP-ThresholdsPrachInfoList-r13,  mpdcch-startSF-CSS-RA-r13 CHOICE {  fdd-r13  ENUMERATED {v1, v1dot5, v2, v2dot5, v4, v5, v8,  v10},  tdd-r13  ENUMERATED {v1, v2, v4, v5, v8, v10, v20, spare}  }       OPTIONAL, -- Cond MP  prach-HoppingOffset-r13  INTEGER (0..94) OPTIONAL, -- Need OR  prach-ParametersListCE-r13 PRACH-ParametersListCE-r13 } PRACH-Config ::= SEQUENCE { rootSequenceIndex  INTEGER (0..837),  prach-ConfigInfo PRACH-ConfigInfo     OPTIONAL - - Need ON } PRACH-Config-v1310 ::=SEQUENCE {  rsrp-ThresholdsPrachInfoList-r13  RSRP-ThresholdsPrachInfoList-r13  OPTIONAL, -- Cond HO mpdcch-startSF-CSS-RA-r13 CHOICE {   fdd-r13  ENUMERATED {v1, v1dot5,v2, v2dot5, v4, v5, v8,  v10},   tdd-r13  ENUMERATED {v1, v2, v4, v5,v8, v10, v20, spare}  }        OPTIONAL, -- Cond MP prach-HoppingOffset-r13  INTEGER (0..94)  OPTIONAL, -- Need OR prach-ParametersListCE-r13  PRACH-ParametersListCE-r13  OPTIONAL, --Cond MP  initial-CE-level-r13  INTEGER (0..3)    OPTIONAL -- Need OR }PRACH-ConfigSCell-r10 ::=  SEQUENCE {  prach-ConfigIndex-r10   INTEGER(0..63) } PRACH-ConfigInfo ::= SEQUENCE {  prach-ConfigIndex  INTEGER(0..63),  highSpeedFlag  BOOLEAN,  zeroCorrelationZoneConfig  INTEGER(0..15),  prach-FreqOffset  INTEGER (0..94) } PRACH-ParametersListCE-r13::= SEQUENCE (SIZE (1..maxCE-Level-r13)) OF PRACH- ParametersCE-r13PRACH-ParametersCE-r13 ::= SEQUENCE {  prach-ConfigIndex-r13   INTEGER(0..63),  prach-FreqOffset-r13    INTEGER (0..94), prach-StartingSubframe-r13    ENUMERATED {sf2, sf4, sf8, sf16, sf32,sf64, sf128,     sf256}     OPTIONAL, -- Need OP maxNumPreambleAttemptCE-r13             ENUMERATED {n3, n4, n5, n6, n7,n8, n10} OPTIONAL, - - Need OP  numRepetitionPerPreambleAttempt-r13 ENUMERATED {n1, n2, n4, n8, n16, n32, n64, n128}, mpdcch-NarrowbandsToMonitor-r13  SEQUENCE (SIZE (1..2)) OF  INTEGER(1..maxAvailNarrowBands- r13),  mpdcch-NumRepetition-RA-r13  ENUMERATED{r1, r2, r4, r8, r16,   r32, r64, r128, r256},  prach-HoppingConfig-r13 ENUMERATED {on,off} } RSRP-ThresholdsPrachInfoList-r13 ::= SEQUENCE(SIZE(1..3)) OF RSRP-Range -- ASN1STOP

PRACH-Config field descriptions initial-CE-level Indicates initial PRACHCE level at random access, see TS 36.321 [6]. If not configured, UEselects PRACH CE level based on measured RSRP level, see TS 36.321 [6].highSpeedFlag Parameter: High-speed-flag, see TS 36.211 [21, 5.7.2].TRUE corresponds to Restricted set and FALSE to Unrestricted set.maxNumPreambleAttemptCE Maximum number of preamble transmission attemptsper CE level. See TS 36.321 [6]. mpdcch-NarrowbandsToMonitor Narrowbandsto monitor for MPDCCH for RAR, see TS 36.213 [23, 6.2]. Field values(1..maxAvailNarrowBands-r13) correspond to narrowband indices(0..[maxAvailNarrowBands- r13-1]) as specified in TS 36.211 [21].mpdcch-NumRepetition-RA Maximum number of repetitions for MPDCCH commonsearch space (CSS) for RAR, Msg3 and Msg4, see TS 36.211 [21].mpdcch-startSF-CSS-RA Starting subframe configuration for MPDCCH commonsearch space (CSS), including RAR, Msg3 retransmission, PDSCH withcontention resolution and PDSCH with RRCConnectionSetup, see TS 36.211[21] and TS 36.213 [23]. Value v1 corresponds to 1, value v1dot5corresponds to 1.5, and so on. numRepetitionPerPreambleAttempt Number ofPRACH repetitions per attempt for each CE level, See TS 36.211 [21].prach-ConfigIndex Parameter: proch-ConfigurationIndex, see TS 36.211[21, 5.7.1]. prach-FreqOffset Parameter: proch-FrequencyOffset, see TS36.211 [21, 5.7.1]. For TDD the value range is dependent on the value ofproch-ConfigIndex. prach-HoppingConfig Coverage level specific frequencyhopping configuration for PRACH. prach-HoppingOffset Parameter: PRACHfrequency hopping offset, expressed as a number of resource blocks, seeTS 36.211 [21, 5.7.1] prach-ParametersListCE Configures PRACH parametersfor each CE level. The first entry in the list is the PRACH parametersof CE level 0, the second entry in the list is the PRACH parameters ofCE level 1, and so on. prach-StartingSubframe PRACH starting subframeperiodicity, expressed in number of subframes available for preambletransmission (PRACH opportunities), see TS 36.211 [21]. Value sf2corresponds to 2 subframes, sf4 corresponds to 4 subframes and so on.EUTRAN configures the PRACH starting subframe periodicity larger than orequal to the Number of PRACH repetitions per attempt for each CE level(numRepetitionPerPreambleAttempt). rootSequenceIndex Parameter: RACHROOT SEQUENCE, see TS 36.211 [21, 5.7.1]. rsrp-ThresholdsPrachInfoListThe criterion for BL UEs and UEs in CE to select PRACH resource set. Upto 3 RSRP threshold values are signalled to determine the CE level forPRACH, see TS 36.213 [23]. The first element corresponds to RSRPthreshold 1, the second element corresponds to RSRP threshold 2 and soon, see TS 36.321 [6]. zeroCorrelationZoneConfig Parameter: N_(CS)configuration, see TS 36.211 [21, 5.7.2: table 5.7.2-2] for preambleformat 0..3 and TS 36.211 [21, 5.7.2: table 5.7.2-3] for preamble format4.

Conditional presence Explanation HO The field is mandatory present ifinitial-CE-level-r13 is absent; otherwise it is optional, need OR. MPThe field is mandatory present.[ . . . ]

-   RACH-ConfigCommon    The IE RACH-ConfigCommon is used to specify the generic random    access parameters.

RACH-ConfigCommon Information Element

-- ASN1START RACH-ConfigCommon ::= SEQUENCE {  preambleInfo  SEQUENCE {  numberOfRA-Preambles   ENUMERATED {   n4, n8, n12, n16, n20, n24, n28,  n32, n36, n40, n44, n48, n52, n56,   n60, n64},  preamblesGroupAConfig   SEQUENCE {    sizeOfRA-PreamblesGroupA   ENUMERATED {    n4, n8, n12, n16, n20, n24, n28,    n32, n36, n40,n44, n48, n52, n56,    n60},    messageSizeGroupA     ENUMERATED {b56,b144, b208, b256},    messagePowerOffsetGroupB   ENUMERATED {  minusinfinity, dB0, dB5, dB8, dB10, dB12,   dB15, dB18},    ...   }   OPTIONAL          -- Need OP  },  powerRampingParameters PowerRampingParameters,  ra-SupervisionInfo  SEQUENCE {  preambleTransMax   PreambleTransMax,   ra-ResponseWindowSize  ENUMERATED {   sf2, sf3, sf4, sf5, sf6, sf7,   sf8, sf10},  mac-ContentionResolutionTimer    ENUMERATED {   sf8, sf16, sf24, sf32,sf40, sf48,   sf56, sf64}  },  maxHARQ-Msg3Tx INTEGER (1..8),  ...,  [[preambleTransMax-CE-r13   PreambleTransMax  OPTIONAL, -- Need OR  rach-CE-LevelInfoList-r13 RACH-CE-LevelInfoList-r13    OPTIONAL - -Need OR  ]] } RACH-ConfigCommon-v1250 ::= SEQUENCE {  txFailParams-r12SEQUENCE {   connEstFailCount-r12   ENUMERATED {n1, n2, n3, n4},  connEstFailOffsetValidity-r12    ENUMERATED {s30, s60, s120, s240,   s300, s420, s600, s900},   connEstFailOffset-r12   INTEGER(0..15)   OPTIONAL -- Need OP  } } RACH-ConfigCommonSCell-r11 ::=SEQUENCE {  powerRampingParameters-r11   PowerRampingParameters, ra-SupervisionInfo-r11  SEQUENCE {   preambleTransMax-r11  PreambleTransMax  },  ... } RACH-CE-LevelInfoList-r13 ::= SEQUENCE(SIZE (1..maxCE-Level-r13)) OF RACH- CE-LevelInfo-r13RACH-CE-LevelInfo-r13 ::= SEQUENCE {  preambleMappingInfo-r13   SEQUENCE{   firstPreamble-r13   INTEGER (0..63),   lastPreamble-r13   INTEGER(0..63)  },  ra-ResponseWindowSize-r13 ENUMERATED {sf20, sf50, sf80,sf120, sf180,    sf240, sf320, sf400}, mac-ContentionResolutionTimer-r13   ENUMERATED {sf80, sf100, sf120,   sf160, sf200, sf240, sf480, sf960},  rar-HoppingConfig-r13 ENUMERATED{on,off},  ... } PowerRampingParameters ::= SEQUENCE {  powerRampingStepENUMERATED {dB0, dB2, dB4, dB6},  preambleInitialReceivedTargetPower ENUMERATED { dBm-120, dBm-118, dBm-116, dBm-114, dBm- 112, dBm-110,dBm-108, dBm-106, dBm-104, dBm- 102, dBm-100, dBm-98, dBm-96, dBm-94,dBm-92, dBm-90} } PreambleTransMax ::= ENUMERATED {  n3, n4, n5, n6, n7,n8, n10, n20, n50,  n100, n200} -- ASN1STOP

RACH-ConfigCommon field descriptions connEstFailCount Number of timesthat the UE detects T300 expiry on the same cell before applyingconnEstFailOffset. connEstFailOffset Parameter “Qoffset_(temp)” in TS36.304 [4]. If the field is not present the value of infinity shall beused for “Qoffset_(temp)”. connEstFailOffsetValidity Amount of time thatthe UE applies connEstFailOffset before removing the offset fromevaluation of the cell. Value s30 corresponds to 30 seconds, s60corresponds to 60 seconds, and so on. mac-ContentionResolution TimerTimer for contention resolution in TS 36.321 [6]. Value in subframes.Value sf8 corresponds to 8 subframes, sf16 corresponds to 16 subframesand so on. maxHARQ-Msg3Tx Maximum number of Msg3 HARQ transmissions inTS 36.321 [6], used for contention based random access. Value is aninteger. messagePowerOffsetGroupB Threshold for preamble selection in TS36.321 [6]. Value in dB. Value minusinfinity corresponds to −infinity.Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on.messageSizeGroupA Threshold for preamble selection in TS 36.321 [6].Value in bits. Value b56 corresponds to 56 bits, b144 corresponds to 144bits and so on. numberOfRA-Preambles Number of non-dedicated randomaccess preambles in TS 36.321 [6]. Value is an integer. Value n4corresponds to 4, n8 corresponds to 8 and so on. powerRampingStep Powerramping factor in TS 36.321 [6]. Value in dB. Value dB0 corresponds to 0dB, dB2 corresponds to 2 dB and so on. connEstFailCount Number of timesthat the UE detects T300 expiry on the same cell before applyingconnEstFailOffset. preambleInitialReceivedTargetPower Initial preamblepower in TS 36.321 [6]. Value in dBm. Value dBm-120 corresponds to −120dBm, dBm-118 corresponds to −118 dBm and so on. preambleMappingInfoProvides the mapping of premables to groups for each CE level, asspecified in TS 36.321 [6]. preamblesGroupAConfig Provides theconfiguration for preamble grouping in TS 36.321 [6]. If the field isnot signalled, the size of the random access preambles group A [6] isequal to numberOfRA-Preambles. preambleTransMax, preambleTransMax-CEMaximum number of preamble transmission in TS 36.321 [6]. Value is aninteger. Value n3 corresponds to 3, n4 corresponds to 4 and so on.rach-CE-LevelInfoList Provides RACH information each coverage level. Thefirst entry in the list is the contention resolution timer of CE level0, the second entry in the list is the contention resolution timer of CElevel 1, and so on. If E-UTRAN includes rach-CE-LevelInfoList, itincludes the same number of entries as in prach-ParametersListCE.ra-ResponseWindowSize Duration of the RA response window in TS 36.321[6]. Value in subframes. Value sf2 corresponds to 2 subframes, sf3corresponds to 3 subframes and so on. The same value applies for eachserving cell (although the associated functionality is performedindependently for each cell). rar-HoppingConfig Frequency hoppingactivation/deactivation for RAR/Msg3/Msg4 for a CE level, see TS 36.211[21]. connEstFailCount Number of times that the UE detects T300 expiryon the same cell before applying connEstFailOffset.sizeOfRA-PreamblesGroupA Size of the random access preambles group A inTS 36.321 [6]. Value is an integer. Value n4 corresponds to 4, n8corresponds to 8 and so on.

In LTE, a transmission on PRACH is specified in 3GPP TS 36.211.

Based on the current agreement for bandwidth part in NR mentioned above,a UE is only assumed to receive or transmit within active DL (Downlink)or UL (Uplink) bandwidth part(s) using the associated numerology, atleast PDSCH (Physical Downlink Shared Channel) and/or PDCCH (PhysicalDownlink Control Channel) for DL and PUCCH and/or PUSCH for UL. It hasalso been agreed that numerology for RACH (Random Access Channel)preamble can be different from or the same as that for the other ULdata/control channels.

In general, to perform a RACH transmission, a UE needs to select anavailable RACH resource (or a RACH opportunity) based on RACHconfiguration(s). In addition, a UE may be configured with one ormultiple bandwidth parts (BWPs) and one of BWPs may be active (oractivated). It may also be possible that multiple BWPs are active (oractivated). One BWP is associated with a specific numerology. DifferentBWPs may associate with the same or different numerologies. RACHresources (or opportunities) may or may not be available in thecurrently active BWP of the UE.

Performing a RACH transmission (or selecting a RACH resource oropportunity) outside the currently active BWP requires RF (RadioFrequency) retuning and causes interruption. The UE generally needs toretune its RF from the currently active BWP to the frequency of theselected RACH resource or opportunity before performing the RACHtransmission. During the RF retuning, the UE is not able to perform atransmission or a reception. Interruption is thus caused due to RFretuning. The interruption can last for a period of time, e.g. tens ofmicro-seconds to hundreds of micro-seconds. The interruption may beinevitable if there is no RACH resources or opportunities that can beused by the UE in the currently active BWP. However, to avoid theinterruption, if there is a RACH resource or opportunity that can beused by the UE in the currently active BWP, it may be preferable for theUE to perform a RACH transmission in the currently active BWP. It seemssimpler and efficient.

A UE should perform a RACH transmission (or select a RACH resource oropportunity) in an active BWP if there is a RACH resource or opportunitythat can be used by the UE in an active BWP. There may be a RACHresource or opportunity that can be used by the UE outside the activeBWP, e.g. in a BWP which is not currently active. The UE may not performa RACH transmission (or select a RACH resource or opportunity) outsidethe active BWP (e.g. in a BWP which is not currently active) if there isa RACH resource/opportunity that can be used by the UE in the activeBWP. The UE may perform a RACH transmission (or select a RACH resourceor opportunity) outside the active BWP (e.g. in a BWP which is notcurrently active) if there is no RACH resource or opportunity that canbe used by the UE in the active BWP. The UE may prioritize (or prefer) aRACH resource or opportunity in the active BWP. The UE may de-prioritizea RACH resource or opportunity outside the active BWP. The UE may selecta RACH resource or opportunity when there is a need to perform a RACHtransmission.

It has been agreed that different PRACH configurations will besupported, e.g. considering different numerologies case and whetherTx/Rx beam correspondence is available or not at gNB. Generally, atleast some RACH configuration should be common to all UEs of a cell,e.g. RACH-ConfigCommon or PRACH-config in LTE (see 3GPP TS 36.331v14.2.0 for more detail). The RACH configuration(s) can be provided bysystem information. The BWP configuration and activation/deactivation ofa BWP is dedicated to a UE. When a UE needs to perform a RACHtransmission, it may need to select a RACH resource or opportunity thatis usable (or preferable) by the UE. For example, a RACH resource oropportunity in the currently active BWP may be considered as usable orpreferable to the UE. However, the UE may not select a RACH resource oropportunity properly if the UE does not know whether a RACH resource oropportunity is in the currently active BWP of the UE.

To solve the problem, the UE needs to know which RACH configuration isassociated with the currently active BWP. There should be an associationbetween a RACH configuration and a BWP, and the association of the RACHconfiguration and the BWP should be provided to the UE. The concept ofthe invention is that a UE is provided with information to associate aRACH configuration with a BWP. The UE performs a RACH transmission (orselects a RACH resource or opportunity) based on the information and/orthe currently active BWP of the UE.

In one embodiment, the information may be a frequency information. Thefrequency information can be used by a UE to associate a BWP with a RACHconfiguration. The BWP may be an active BWP of the UE. The frequencyinformation may be included in a RACH configuration. The frequencyinformation may indicate or derive a frequency (e.g. physical resourceblock (PRB)). The UE may determine that a RACH configuration isassociated with the currently active BWP if the frequency informationindicating (or deriving) a frequency within the currently active BWP.The UE may determine that a RACH configuration is not associated withthe currently active BWP if the frequency information indicating (orderiving) a frequency outside the currently active BWP.

The frequency information may be used to indicate or derive a frequency(e.g. physical resource block (PRB)) of one or more RACH resources oropportunities. The UE may determine whether a RACH resource oropportunity is in the currently active BWP based on the frequencyinformation. For example, if the indicated (or derived) frequency iswithin the frequency range of the currently active BWP, the UE considersthe associated RACH resource or opportunity is in the currently activeBWP. If the indicated (or derived) frequency is not within the frequencyrange of the currently active BWP, the UE considers the associated RACHresource or opportunity is outside the currently active BWP.

An example of associating a RACH configuration with a BWP by frequencyinformation is illustrated in FIG. 5. In this example, systeminformation provides 3 RACH configurations (RACH configuration #1 to#3), and each RACH configuration includes frequency information(frequency information #1 to #3, respectively). The frequencyinformation indicates a frequency location of its corresponding RACHconfiguration. A UE is configured with 3 BWPs (BWP #1 to #3). Based onthe BWP configuration of the UE, frequency information #1 is in BWP#1and BWP#2, frequency information #2 is in BWP#1 and BWP#3, and frequencyinformation #3 is in BWP#1 and BWP #3. Then, when BWP#1 is active, theUE can use RACH configuration #1, #2, and #3 (since BWP#1 coversfrequency information #1, #2, and #3). When BWP#2 is active, the UE canuse RACH configuration #1. When BWP #3 is active, the UE can use RACHconfiguration #2 and #3. Moreover, when no BWP covering a frequencyinformation is active, the UE does not use a RACH configurationcorresponding to the frequency information (at least when there is otherRACH configuration that can be used).

The information may be an index (or an identity) of a RACHconfiguration. The index (or the identity) can be used to identify aRACH configuration. The index (or the identity) may be included insystem information. Alternatively, the index (or the identity) may beimplicitly indicated, and not explicitly included in the systeminformation. For example, the index (or the identity) is indicated bythe structure (or the order) of the RACH configurations included in thesystem information e.g. the first RACH configuration (i.e. RACHconfiguration#1 in FIG. 6) is associated with index 1 and the secondRACH configuration (i.e. RACH configuration#2 in FIG. 6) is associatedwith index 2, and so on.

A BWP configuration can include the index (or the identity) of the RACHconfiguration and associating a BWP with the RACH configuration. The UEmay consider a RACH configuration as usable/preferable if a BWPassociated with the RACH configuration is active. For example, when aBWP is activated, the UE considers the RACH configuration associatedwith the BWP as usable or preferable. When a BWP is deactivated, the UEconsiders the RACH configuration associated with the BWP as not usableor preferable.

In one embodiment, the information may be provided in systeminformation. The information may be included in (or provided along with)a RACH configuration. The information may be included in (or providedalong with) a BWP configuration. The UE may be configured with more thanone BWPs. One of the configured BWPs may be currently active (oractivated). More than one of the configured BWPs may be currently active(or activated). There may be RACH resources available on more than oneBWPs configured to the UE. The UE may be provided with multiple RACHconfigurations. The information is included in each RACH configuration.Each RACH configuration is associated with one information. Each RACHconfiguration is associated with one BWP.

An example of associating a RACH configuration with a BWP by indexinformation is illustrated in FIG. 6. In this example, systeminformation provides 3 RACH configurations (RACH configuration #1 to#3), and each RACH configuration includes index information (index #1 to#3, respectively). The index information identifies a RACHconfiguration. A UE is configured with 3 BWPs (BWP #1 to #3). In the BWPconfiguration, each BWP is associated with one index of RACHconfiguration. It may also be possible that a BWP is associated withmore than one index. When a BWP is active, the UE can use the RACHconfiguration(s) associated with the BWP indicated in the BWPconfiguration. For example, when BWP#1 is active, the UE can use RACHconfiguration #1. When BWP#2 is active, the UE can use RACHconfiguration #2. When BWP #3 is active, the UE can use RACHconfiguration #3. The RACH configuration not associated with thecurrently active BWP should not be used (at least when there is RACHconfiguration that can be used).

In one embodiment, a RACH transmission may be a transmission on PRACH, atransmission of RA preamble, and/or a transmission during a RA (RandomAccess) procedure. A RACH configuration may be a PRACH configuration, aconfiguration related to RACH. A RACH resource may be a time and/orfrequency resource for a RACH transmission. A RACH opportunity may be anopportunity on time and/or frequency domain that can be used by the UEfor a RACH transmission.

FIG. 7 is a flow chart 700 according to one exemplary embodiment of aUE. In step 705, the UE receives information from a network node toassociate a RACH configuration with a BWP among the multiple BWPs. Instep 710, the UE performs a RACH transmission in the BWP using the RACHconfiguration associated with the BWP.

In one embodiment, the UE could determine the RACH configuration isassociated with the BWP if the information is included in aconfiguration of the BWP. The information could identify the RACHconfiguration and the information is included in a BWP configuration.

In one embodiment, the UE could be configured with multiple RACHconfigurations. Each RACH configuration could be associated with one BWPamong the multiple BWPs.

In one embodiment, the UE could perform an UL (Uplink) transmission on aPUSCH (Physical Uplink Shared Channel) in the BWP. More specifically,the UE could perform the UL transmission on the PUSCH in the BWP if aDCI (Downlink Control Information) indicates a scheduling grant isreceived.

In one embodiment, the UE could receive a signalling from the networknode to activate the BWP. The signalling could be a Radio ResourceControl (RRC) signalling, a Downlink Control Information (DCI)indicating a scheduling grant, or a MAC (Medium Access Control) controlelement. The BWP could be a UL BWP. The RACH transmission could be atransmission of a random access preamble.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to receiveinformation from a network node to associate a RACH configuration with aBWP among the multiple BWPs, and (ii) to perform a RACH transmission inthe BWP using the RACH configuration associated with the BWP.Furthermore, the CPU 308 can execute the program code 312 to perform allof the above-described actions and steps or others described herein.

FIG. 8 is a flow chart 800 according to one exemplary embodiment of anetwork node. In step 805, the network node transmits information to aUE to associate a RACH configuration with a BWP. In step 810, thenetwork node receives a RACH transmission in the BWP from the UEaccording to the RACH configuration associated with the BWP.

In one embodiment, the UE could be configured with multiple BWPs and theBWP is among the multiple BWPs. The network node could transmit asignalling to the UE to activate the BWP.

In one embodiment, the UE could receive a signalling from the networknode to activate the BWP. The signalling could be a RRC signalling, aDCI indicating a scheduling grant, or a MAC control element. The BWPcould be a UL (Uplink) BWP. The RACH transmission could be atransmission of a random access preamble.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of anetwork node, the device 300 includes a program code 312 stored in thememory 310. The CPU 308 could execute program code 312 to enable thenetwork node (i) to transmit information to a UE to associate a RACHconfiguration with a BWP, and (ii) to receive a RACH transmission in theBWP from the UE according to the RACH configuration associated with theBWP. Furthermore, the CPU 308 can execute the program code 312 toperform all of the above-described actions and steps or others describedherein.

FIG. 9 is a flow chart 900 according to one exemplary embodiment of anetwork node. In step 905, the network transmits, to a UE, informationto associate a RACH configuration with a BWP.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of anetwork, the device 300 includes a program code 312 stored in the memory310. The CPU 308 could execute program code 312 to enable the network totransmit, to a UE, information to associate a RACH configuration with aBWP. Furthermore, the CPU 308 can execute the program code 312 toperform all of the above-described actions and steps or others describedherein.

FIG. 10 is a flow chart 1000 according to one exemplary embodiment of aUE. In step 1005, the UE obtains information to associate a RACHconfiguration with a BWP. In one embodiment, the BWP could be an activeBWP of the UE.

In step 1010, the UE performs a RACH transmission in the BWP using theRACH configuration associated with the BWP. In one embodiment, the UEcould determine whether the RACH configuration is associated with anactive BWP of the UE based on the information.

In one embodiment, the UE could select a RACH resource for the RACHtransmission based on the information, e.g. selecting the RACH resourceassociated with an active BWP of the UE. Alternatively or additionally,the UE could select a RACH opportunity for the RACH transmission basedon the information, e.g. selecting the RACH opportunity associated withan active BWP of the UE.

In one embodiment, the UE could prioritize a RACH configuration, a RACHresource, or a RACH opportunity associated with an active BWP of the UEfor the RACH transmission.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to obtaininformation to associate a RACH configuration with a BWP, and (ii) toperform a RACH transmission in the BWP using the RACH configurationassociated with the BWP. Furthermore, the CPU 308 can execute theprogram code 312 to perform all of the above-described actions and stepsor others described herein.

In one embodiment, the information could include frequency information.Alternatively or additionally, the information could be included in theRACH configuration. Alternatively or additionally, the information couldindicate or derive a frequency, e.g. physical resource block.

In one embodiment, the UE could associate a RACH configuration with aBWP if the information for the RACH configuration indicating a frequencywithin the BWP. The UE could determine the RACH configuration isassociated with an active BWP if the frequency is within the active BWP.The UE could determine the RACH configuration is not associated with anactive BWP if the frequency is outside the active BWP.

In one embodiment, the information could include an index (or anidentity) of a RACH configuration. The information could identify a RACHconfiguration. The information could be included in a BWP configuration.

In one embodiment, the UE could associate a RACH configuration with aBWP if the information for the RACH configuration is included in aconfiguration of the BWP. The UE could determine the RACH configurationis associated with an active BWP if the information is included in aconfiguration of an active BWP. The UE could determine the RACHconfiguration is not associated with an active BWP if the information isnot included in a configuration of an active BWP.

In one embodiment, the information could be included in systeminformation. The information could be implicitly indicated by the RACHconfiguration. The information could be implicitly indicated by sequenceof the RACH configuration included in system information.

In one embodiment, the UE could obtain the information by receiving theinformation, or by deriving the information from system information. TheUE could be configured with more than one BWPs.

In one embodiment, at least one of the configured BWPs is active. TheRACH resources are available on more than one configured BWPs. The UEcould be provided with more than one RACH configurations.

In one embodiment, each RACH configuration could include theinformation. Each RACH configuration could be associated with a BWP.

In one embodiment, the RACH transmission could be a transmission on aPRACH (Physical Random Access Channel), a transmission of RA (RandomAccess) preamble, or a transmission during a RA procedure. The RACHconfiguration could include a configuration of a PRACH. The RACHconfiguration could include a configuration related to a RACH (RandomAccess Channel). The RACH resource could include a time and/or frequencyresource for a RACH transmission. The RACH opportunity could include anopportunity on time and/or frequency domain that can be used by the UEfor a RACH transmission.

In one embodiment, the BWP could be a UL BWP and/or DL BWP. The BWPcould indicate a bandwidth for transmission and/or reception. The BWPconfiguration could include a bandwidth, e.g. number of PRBs. The BWPconfiguration could also include a frequency location, e.g. centerfrequency. Furthermore, the BWP configuration could include anumerology.

In one embodiment, the active BWP could be a BWP configured to the UEwhich is activated. The BWP could be activated or deactivated, e.g. viaa network signaling.

In one embodiment, the UE may not be required to perform a transmissionand/or reception outside its active BWP(s). Furthermore, the UE could bein a connected mode. The network node could be a NR gNB.

Various aspects of the disclosure have been described above. It shouldbe apparent that the teachings herein may be embodied in a wide varietyof forms and that any specific structure, function, or both beingdisclosed herein is merely representative. Based on the teachings hereinone skilled in the art should appreciate that an aspect disclosed hereinmay be implemented independently of any other aspects and that two ormore of these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. As an exampleof some of the above concepts, in some aspects concurrent channels maybe established based on pulse repetition frequencies. In some aspectsconcurrent channels may be established based on pulse position oroffsets. In some aspects concurrent channels may be established based ontime hopping sequences. In some aspects concurrent channels may beestablished based on pulse repetition frequencies, pulse positions oroffsets, and time hopping sequences.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, processors, means, circuits, and algorithmsteps described in connection with the aspects disclosed herein may beimplemented as electronic hardware (e.g., a digital implementation, ananalog implementation, or a combination of the two, which may bedesigned using source coding or some other technique), various forms ofprogram or design code incorporating instructions (which may be referredto herein, for convenience, as “software” or a “software module”), orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentdisclosure.

In addition, the various illustrative logical blocks, modules, andcircuits described in connection with the aspects disclosed herein maybe implemented within or performed by an integrated circuit (“IC”), anaccess terminal, or an access point. The IC may comprise a generalpurpose processor, a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, electrical components, opticalcomponents, mechanical components, or any combination thereof designedto perform the functions described herein, and may execute codes orinstructions that reside within the IC, outside of the IC, or both. Ageneral purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

It is understood that any specific order or hierarchy of steps in anydisclosed process is an example of a sample approach. Based upon designpreferences, it is understood that the specific order or hierarchy ofsteps in the processes may be rearranged while remaining within thescope of the present disclosure. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with theaspects disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module (e.g., including executable instructions and relateddata) and other data may reside in a data memory such as RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a harddisk, a removable disk, a CD-ROM, or any other form of computer-readablestorage medium known in the art. A sample storage medium may be coupledto a machine such as, for example, a computer/processor (which may bereferred to herein, for convenience, as a “processor”) such theprocessor can read information (e.g., code) from and write informationto the storage medium. A sample storage medium may be integral to theprocessor. The processor and the storage medium may reside in an ASIC.The ASIC may reside in user equipment. In the alternative, the processorand the storage medium may reside as discrete components in userequipment. Moreover, in some aspects any suitable computer-programproduct may comprise a computer-readable medium comprising codesrelating to one or more of the aspects of the disclosure. In someaspects a computer program product may comprise packaging materials.

While the invention has been described in connection with variousaspects, it will be understood that the invention is capable of furthermodifications. This application is intended to cover any variations,uses or adaptation of the invention following, in general, theprinciples of the invention, and including such departures from thepresent disclosure as come within the known and customary practicewithin the art to which the invention pertains.

The invention claimed is:
 1. A method for a User Equipment (UE), whereinthe UE is configured with multiple Bandwidth Parts (BWPs) in onecomponent carrier, comprising: receiving information from a network nodeto associate a first RACH (Random Access Channel) configuration with afirst BWP for at least one of the multiple BWPs of the one componentcarrier; determining whether there is a second RACH configurationassociated with a currently active BWP after receiving the information;and selecting a RACH resource to perform a RACH transmission based uponwhether a second RACH configuration is associated with the currentlyactive BWP.
 2. The method of claim 1, wherein the UE determines thesecond RACH configuration is associated with the currently active BWP ifthe second RACH configuration is included in a configuration of thecurrently active BWP.
 3. The method of claim 1, wherein the informationidentifies the first RACH configuration.
 4. The method of claim 1,wherein each RACH configuration is associated with one BWP among themultiple BWPs.
 5. The method of claim 1, wherein the UE is configuredwith multiple RACH configurations.
 6. The method of claim 1, wherein theUE performs an UL (Uplink) transmission on a PUSCH (Physical UplinkShared Channel) in the currently active BWP.
 7. The method of claim 1,further comprising: the UE receives a signalling from the network nodeto activate a BWP.
 8. The method of claim 1, wherein the RACHtransmission is a transmission of a random access preamble.
 9. A methodfor a network node, comprising: transmitting information to a UserEquipment (UE) to associate a first Random Access Channel (RACH)configuration with a first Bandwidth Part (BWP) for at least one ofmultiple BWPs in one component carrier; receiving a RACH transmission ina currently active BWP from the UE according to a second RACHconfiguration if the second RACH configuration is associated with thecurrently active BWP; and receiving a RACH transmission in a second BWPwhich is not the currently active BWP if no RACH configuration isassociated with the currently active BWP.
 10. The method of claim 9,wherein the UE is configured with the multiple BWPs in the one componentcarrier and the BWP is among the multiple BWPs.
 11. The method of claim9, further comprising: the network node transmits a signalling to the UEto activate a BWP.
 12. The method of claim 11, wherein the signalling isa Radio Resource Control (RRC) signalling, a Downlink ControlInformation (DCI) indicating a scheduling grant, or a MAC (Medium AccessControl) control element.
 13. A User Equipment (UE), wherein the UE isconfigured with multiple Bandwidth Parts (BWPs) in one componentcarrier, comprising: a control circuit; a processor installed in thecontrol circuit; and a memory installed in the control circuit andoperatively coupled to the processor; wherein the processor isconfigured to execute a program code stored in the memory to: receiveinformation from a network node to associate a first RACH (Random AccessChannel) configuration with a first BWP for at least one of the multipleBWPs of the one component carrier; determine whether there is a secondRACH configuration associated with a currently active BWP afterreceiving the information; and select a RACH resource to perform a RACHtransmission based upon whether a second RACH configuration isassociated with the currently active BWP.
 14. The UE of claim 13,wherein the UE determines the second RACH configuration is associatedwith the currently active BWP if the information is included in aconfiguration of the currently active BWP.
 15. The UE of claim 13,wherein the information identifies the first RACH configuration.
 16. TheUE of claim 13, wherein each RACH configuration is associated with oneBWP among the multiple BWPs.
 17. The UE of claim 13, wherein the UE isconfigured with multiple RACH configurations.
 18. The UE of claim 13,wherein the UE performs an UL (Uplink) transmission on a PUSCH (PhysicalUplink Shared Channel) in the currently active BWP.
 19. The UE of claim13, further comprising: the UE receives a signalling from the networknode to activate a BWP.
 20. The UE of claim 13, wherein the RACHtransmission is a transmission of a random access preamble.
 21. Anetwork node, comprising: a control circuit; a processor installed inthe control circuit; and a memory installed in the control circuit andoperatively coupled to the processor; wherein the processor isconfigured to execute a program code stored in the memory to: transmitinformation to a User Equipment (UE) to associate a first Random AccessChannel (RACH) configuration with a first Bandwidth Part (BWP) for atleast one of multiple BWPs in one component carrier; receive a RACHtransmission in a currently active BWP from the UE according to a secondRACH configuration if the second RACH configuration is associated withthe currently active BWP; and receive a RACH transmission in a secondBWP which is not the currently active BWP if no RACH configuration isassociated with the currently active BWP.
 22. The network node of claim21, wherein the UE is configured with the multiple BWPs in the onecomponent carrier and the BWP is among the multiple BWPs.
 23. Thenetwork node of claim 21, further comprising: the network node transmitsa signalling to the UE to activate a BWP.
 24. The network node of claim23, wherein the signalling is a Radio Resource Control (RRC) signalling,a Downlink Control Information (DCI) indicating a scheduling grant, or aMAC (Medium Access Control) control element.